System and method for generating signal coverage information from client metrics

ABSTRACT

Embodiments may include receiving signal strength information reported by multiple client communication devices. The signal strength information reported by a given client device may indicate one or more locations detected by the given client device. The signal strength information may also indicate, for each location, a respective measure of signal strength for a communication signal detected at that location by the client device. Embodiments may also include generating a signal strength map for a region based on the client-reported signal strength information. Generating the signal strength map may include, for each location of multiple locations within the region, generating an expected signal strength value for that location based on an evaluation of the signal strength information received for that location. The generation of the signal strength map for the region may also be based on the expected signal strength values for the locations within the region.

This application is a continuation of U.S. patent application Ser. No.13/489,260, filed Jun. 5, 2012, now U.S. Pat. No. 9,441,975, which ishereby incorporated by reference herein in its entirety.

BACKGROUND

Technical Field

This disclosure relates generally to navigation, and, more specifically,to functionality of devices providing route navigation.

Description of the Related Art

Navigation capability can be found in a number of electronic devicesincluding personal navigation devices, such as handheld GlobalPositioning System (GPS) Devices, as well as mobile phones that have GPSfunctionality. One common use for navigation-enabled devices includesnavigating from an origination to a destination. For instance, a usermay input a destination street address to the device, and the device maygenerate a suggested route that the user should travel from the user'scurrent destination to arrive at the destination address. Generally, asthe user travels the route, the device may graphically and/or audiblyspecify directional changes along the route, such as “turn right onSmith St. in 100 yards.” One type of navigation device includes on-boardnavigation devices. Onboard navigation devices include map informationthat has been stored on the device prior to route navigation; generallythe map information is stored in an onboard device's internal memory bythe manufacturer. In some cases, additional or substitute mapinformation may be added to an onboard navigation device by a user, suchas by installation of memory card containing map information.

SUMMARY OF EMBODIMENTS

Embodiments of a system and method for generating signal coverageinformation from client metrics are described. Embodiments may includereceiving signal strength information reported by multiple clientcommunication devices. The signal strength information reported by agiven client device may indicate one or more locations detected by thegiven client device. The signal strength information may also indicate,for each location, a respective measure of signal strength for acommunication signal detected at that location by the client device. Forinstance, in one non-limiting example a smartphone may determine itscurrent location using the Global Positioning System (GPS) and reportthat location along with a measure of cellular signal strength at thatlocation.

Embodiments may also include generating a signal strength map for aregion based on the client-reported signal strength information. In onenon-limiting example, such a map may be a heat map of varying signalstrengths. Generating the signal strength map may include, for eachlocation of multiple locations within the region, generating an expectedsignal strength value for that location based on an evaluation of thesignal strength information received for that location. For instance,for a given location (e.g., a specific point position or a region ofmultiple locations), embodiments may generate the mean or median signalstrength value for that location. The generation of the signal strengthmap for the region may be based on the expected signal strength valuesthat are generated. For instance, a signal strength map may be generatedby storing all the mean or median expected signal strength values fordifferent locations into a data structure that represents or defines thesignal strength map. In another example, embodiments may includegenerating the signal strength map as a database of different locationsmapped to associated expected signal strength values. In variousembodiments, the signal strength map for a region may be evaluated todetermine the expected signal strength for any location within thatregion.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates a block diagram illustrating a portablemultifunction device with a touch-sensitive display in accordance withsome embodiments.

FIG. 1B illustrates a block diagram illustrating example components forevent handling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 illustrates a portable multifunction device configured withnavigation route guidance in accordance with some embodiments.

FIG. 4 illustrates a map service operating environment in accordancewith some embodiments.

FIG. 5A illustrates a data flow diagram for collecting location andsignal strength information from a portable multifunction device inaccordance with some embodiments.

FIG. 5B illustrates a data flow diagram for generating a heat map fromaggregated signal strength information in accordance with someembodiments.

FIG. 5C illustrates a flowchart of an example method for generating aheat map from aggregated signal strength information in accordance withsome embodiments.

FIG. 6A illustrates a data flow diagram for analyzing a route and signalstrength heat map to generated a map tile priority in accordance withsome embodiments.

FIG. 6B illustrates the analysis of a signal strength heat map toidentify weak or dead zones in signal strength along a route inaccordance with some embodiments.

FIG. 6C illustrates a flowchart of an example method for analyzing aroute and signal strength heat map to generate a map tile priority inaccordance with some embodiments.

FIG. 7A illustrates a flow diagram of a client device acquiring maptiles in accordance with a map tile priority, according to someembodiments.

FIG. 7B illustrates a flowchart for acquiring map tiles in accordancewith a map tile priority, according to some embodiments.

FIG. 7C illustrates a flowchart for acquiring map tiles in accordancewith a check-pointing technique, according to some embodiments.

FIG. 8 illustrates a flowchart of an example method managing a cachebased on a map tile priority, in accordance with some embodiments.

FIG. 9 illustrates an example computer system configured to implementaspects of the system and method for generating signal coverageinformation from client metrics.

This specification includes references to “one embodiment” or “anembodiment.” The appearances of the phrases “in one embodiment” or “inan embodiment” do not necessarily refer to the same embodiment.Particular features, structures, or characteristics may be combined inany suitable manner consistent with this disclosure.

“Comprising.” This term is open-ended. As used in the appended claims,this term does not foreclose additional structure or steps. Consider aclaim that recites: “An apparatus comprising one or more processor units. . . .” Such a claim does not foreclose the apparatus from includingadditional components (e.g., a network interface unit, graphicscircuitry, etc.).

“Configured To.” Various units, circuits, or other components may bedescribed or claimed as “configured to” perform a task or tasks. In suchcontexts, “configured to” is used to connote structure by indicatingthat the units/circuits/components include structure (e.g., circuitry)that performs those task or tasks during operation. As such, theunit/circuit/component can be said to be configured to perform the taskeven when the specified unit/circuit/component is not currentlyoperational (e.g., is not on). The units/circuits/components used withthe “configured to” language include hardware—for example, circuits,memory storing program instructions executable to implement theoperation, etc. Reciting that a unit/circuit/component is “configuredto” perform one or more tasks is expressly intended not to invoke 35U.S.C. § 112, sixth paragraph, for that unit/circuit/component.Additionally, “configured to” can include generic structure (e.g.,generic circuitry) that is manipulated by software and/or firmware(e.g., an FPGA or a general-purpose processor executing software) tooperate in manner that is capable of performing the task(s) at issue.“Configure to” may also include adapting a manufacturing process (e.g.,a semiconductor fabrication facility) to fabricate devices (e.g.,integrated circuits) that are adapted to implement or perform one ormore tasks.

“First,” “Second,” etc. As used herein, these terms are used as labelsfor nouns that they precede, and do not imply any type of ordering(e.g., spatial, temporal, logical, etc.). For example, a buffer circuitmay be described herein as performing write operations for “first” and“second” values. The terms “first” and “second” do not necessarily implythat the first value must be written before the second value.

“Based On.” As used herein, this term is used to describe one or morefactors that affect a determination. This term does not forecloseadditional factors that may affect a determination. That is, adetermination may be solely based on those factors or based, at least inpart, on those factors. Consider the phrase “determine A based on B.”While in this case, B is a factor that affects the determination of A,such a phrase does not foreclose the determination of A from also beingbased on C. In other instances, A may be determined based solely on B.

DETAILED DESCRIPTION

Introduction

Various embodiments of a system and method for generating signalcoverage information from client metrics are described. Embodiments mayinclude receiving signal strength information reported by multipleclient communication devices (e.g., mobile phones, smart phones, tabletdevices or other portable multifunction devices). For instance, a givenclient device may report messages at different locations to anetwork-service; each message may indicate one or more locationsdetected by the given client device as well as measured signal strengthat those locations. For instance, in one non-limiting example asmartphone may determine use a GPS module to determine specificcoordinates of the smartphone and report those coordinates along with ameasure of cellular signal strength measured at (or proximate to) thelocation specified by the coordinates.

Embodiments may also include generating a signal strength map for aregion based on the client-reported signal strength information. In onenon-limiting example, such a map may be a heat map of varying signalstrengths. For instance, the heat map of signal strength values may begenerated graphically to quickly convey the signal strength information.In other case, the signal strength map may be generated as a specificdata structure or database for automated evaluation of signal strengthvalues at different locations. Generating the signal strength map mayinclude, for each location of multiple locations within the region,generating an expected signal strength value for that location based onan evaluation of the signal strength information received for thatlocation. For instance, for a given location, embodiments may generatethe mean or median signal strength value for that location. Forinstance, to keep the signal strength map current, a calculation of meanor median signal strength values may be based on the n-most (n beingconfigurable) measured signal strength values for a given location. Thegeneration of the signal strength map for the region may be based on theexpected signal strength values that are generated. For instance, asignal strength map may be generated by storing all the mean or medianexpected signal strength values for different locations into a datastructure that represents or defines the signal strength map. In anotherexample, embodiments may include generating the signal strength map as adatabase of different locations mapped to associated expected signalstrength values. In various embodiments, the signal strength map for aregion may be evaluated to determine the expected signal strength forany location within that region. For instance, if the signal strengthmap is structured as a database, the database may be queried for one ormore locations of a region, and the database may return the expectedsignal strength values for those locations.

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present embodiments. However, it will beapparent to one of ordinary skill in the art that the presentembodiments may be practiced without these specific details. In otherinstances, well-known methods, procedures, components, circuits, andnetworks have not been described in detail so as not to unnecessarilyobscure aspects of various embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the intended scope of the presentembodiments. The first contact and the second contact are both contacts,but they are not the same contact.

The terminology used in the description presented herein is for thepurpose of describing particular embodiments only and is not intended tobe limiting of. As used in the present description and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Example Multifunction Device

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the device is a gaming computer withorientation sensors (e.g., orientation sensors in a gaming controller).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and may also be knownas or called a touch-sensitive display system. Device 100 may includememory 102 (which may include one or more computer readable storagemediums), memory controller 122, one or more processing units (CPU's)120, peripherals interface 118, RF circuitry 108, audio circuitry 110,speaker 111, microphone 113, input/output (I/O) subsystem 106, otherinput or control devices 116, and external port 124. Device 100 mayinclude one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIG. 1A may be implemented in hardware,software, or a combination of both hardware and software, including oneor more signal processing and/or application specific integratedcircuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU 120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may be implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of multiple communications standards, protocols and technologies,including but not limited to Global System for Mobile Communications(GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packetaccess (HSDPA), high-speed uplink packet access (HSDPA), wideband codedivision multiple access (W-CDMA), code division multiple access (CDMA),time division multiple access (TDMA), Bluetooth, Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input controldevices 116 may include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 may becoupled to any (or none) of the following: a keyboard, infrared port,USB port, and a pointer device such as a mouse. The one or more buttons(e.g., 208, FIG. 2) may include an up/down button for volume control ofspeaker 111 and/or microphone 113. The one or more buttons may include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any ofmultiple touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image may be obtained for videoconferencingwhile the user views the other video conference participants on thetouch screen display.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. In some embodiments, the proximity sensor turnsoff and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 includes one or more orientation sensors 168. In someembodiments, the one or more orientation sensors include one or moreaccelerometers (e.g., one or more linear accelerometers and/or one ormore rotational accelerometers). In some embodiments, the one or moreorientation sensors include one or more gyroscopes. In some embodiments,the one or more orientation sensors include one or more magnetometers.In some embodiments, the one or more orientation sensors include one ormore of global positioning system (GPS), Global Navigation SatelliteSystem (GLONASS), and/or other global navigation system receivers. TheGPS, GLONASS, and/or other global navigation system receivers may beused for obtaining information concerning the location and orientation(e.g., portrait or landscape) of device 100. In some embodiments, theone or more orientation sensors include any combination oforientation/rotation sensors. FIG. 1A shows the one or more orientationsensors 168 coupled to peripherals interface 118. Alternately, the oneor more orientation sensors 168 may be coupled to an input controller160 in I/O subsystem 106. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more orientationsensors.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detect contact on a touchpad.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which may be made up of a        video player    -   module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of

contacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference 139, e-mail 140, or IM 141; and soforth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of multiple communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 1493, alarmclock widget 149-4, and dictionary widget 149-5) or created by the user(e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 may include the functionality ofan MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. In some embodiments, memory 102 maystore a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,orientation sensor(s) 168, and/or microphone 113 (through audiocircuitry 110). Information that peripherals interface 118 receives fromI/O subsystem 106 includes information from touch-sensitive display 112or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes multiple event handlers190 and one or more application views 191, each of which includesinstructions for handling touch events that occur within a respectiveview of the application's user interface. Each application view 191 ofthe application 136-1 includes one or more event recognizers 180.Typically, a respective application view 191 includes multiple eventrecognizers 180. In other embodiments, one or more of event recognizers180 are part of a separate module, such as a user interface kit (notshown) or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 may utilize or call data updater 176, objectupdater 177 or GUI updater 178 to update the application internal state192. Alternatively, one or more of the application views 191 includesone or more respective event handlers 190. Also, in some embodiments,one or more of data updater 176, object updater 177, and GUI updater 178are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, includes a first touch (touch begin) on thedisplayed object for a predetermined phase, a first lift-off (touch end)for a predetermined phase, a second touch (touch begin) on the displayedobject for a predetermined phase, and a second lift-off (touch end) fora predetermined phase. In another example, the definition for event 2(187-2) is a dragging on a displayed object. The dragging, for example,includes a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making a gesture on the graphics, for example,with one or more fingers 202 (not drawn to scale in the figure) or oneor more styluses 203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thegesture may include one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some embodiments, inadvertentcontact with a graphic may not select the graphic. For example, a swipegesture that sweeps over an application icon may not select thecorresponding application when the gesture corresponding to selection isa tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 100 also may accept verbal inputfor activation or deactivation of some functions through microphone 113.

It should be noted that, although many of the following examples will begiven with reference to inputs on touch screen 112 (where the touchsensitive surface and the display are combined), a touch-sensitivesurface that is separate from the display may be used instead of touchscreen 112.

Example Mapping Functionality

FIG. 3 illustrates another example of a multifunction device, which maybe configured in a manner similar to the multifunction device describedabove. In the illustrated embodiment, a multifunction device 300includes a mapping application (e.g., map module 154 described above)that may be stored in one or more memories of multifunction device 300and executed on one or more processors of multifunction device 300. Asis the case for the multifunction device described above, multifunctiondevice 300 may include one or more controls 302 for operating themultifunction device. These controls may include but are not limited topower controls for turning the device on and off, volume controls foradjusting the ear piece volume or the speaker volume, menu controls fornavigation functions of the device, and function controls for initiatingone or more function or actions on the device. Controls 302 may includehardware controls or software controls. For instance, the bottom leftcorner of electronic display 312 includes a graphical representation ofa control 312 that may be selected by a user, such as by way of touch inaccordance with the touch screen functionality described above.Multifunction device 300 may also include other components similar tothose described above, such as a microphone 304, an earpiece 306 (e.g.,a speaker through which to convey audio representations of telephonecalls), an optical sensor 308, and/or a speaker 310. Each of thesecomponents may be configured in a similar manner to those like-namedcomponents of FIG. 2 described above. Furthermore, electronic display312 may be configured with touch screen capability, such as touch screen112 described above. In various embodiments, controls (e.g., on screencontrol(s) 302) may be utilized to perform any of a variety ofmap-related functions including but not limited to zoom in, zoom out,rotate screen, pan screen, toggle views (e.g., two-dimensions to threedimensions and vice versa), and/or another map related activity. Invarious embodiments, one or more gestures may be utilized to perform anyof the aforesaid map controls (with or without the use of an actualgraphical on-screen control). In one non-limiting example, a one figuregesture may be utilized to adjust the pitch within a three-dimensionalmap view.

As noted above, multifunction device 300 includes a mapping applicationthat may be stored in one or more memories of multifunction device 300and executed on one or more processors of multifunction device 300. Inthe illustrated embodiment, the graphical representation of the mappingapplication may include a map 314 a of a geographic region. This map maybe presented as a two-dimensional map or a three-dimensional map, theselection of which may be specified through, e.g., a user-configurableparameter of the mapping application. In some embodiments, themultifunction device may toggle between two-dimensional map orthree-dimensional map views responsive to input from any input componentof the multifunction device. In one non-limiting example, input fromorientation sensor(s) 168 may initiate the transition from atwo-dimensional map view to a three-dimensional map, and vice versa. Forinstance, one or more of orientation sensor(s) 168 may detect a tilt(e.g., a user-initiated tilt) in the orientation of the multifunctiondevice and, in response, initiate the aforesaid toggling.

Map 314 a may include a graphical position indicator 316, which mayrepresent the location of the multifunction device within the geographicregion of the map. Generally position indicator 316 may represent thecurrent or real-time position of the multifunction device, although itshould be understood that in some cases there may exist some smallamount of temporal latency between the actual position of themultifunction device and the graphical representation of that location(e.g., position indicator 316). This may occur, e.g., when themultifunction device is in motion. In various embodiments, themultifunction device may be configured to perform map matching includingbut not limited to aligning a sequence of observed user positions with aroad network on a digital map. In various embodiments, the multifunctiondevice may be configured to perform a “snap to” function in which thegraphical position indicator 316 is aligned onto a roadway when theuser's position falls within in a specified threshold distance of theroadway.

Furthermore, multifunction device 300 may generally be operated by auser. For example, multifunction device 300 may in some cases be asmartphone utilized by an individual to make phone calls, send textmessages, browse the internet, etc. As use of multifunction device by anindividual generally implies the individual is proximate to themultifunction device (e.g., the user may be holding the device in his orher hand), references herein to the location of the device and thelocation of the user may be considered to be synonymous. However, itshould be understood that in some cases the actual position of themultifunction device and the user of that device may differ by somedistance. For instance, the user may place his or her multifunctiondevice on a table of an outdoor café while sitting in a nearby chair. Inthis case, the position of the device and the position of the user maydiffer by some small amount. In another example, multifunction device300 may be mounted on a car dashboard (e.g., for use as a navigationdevice) while the user of the device sits nearby (e.g., in the driverseat of the car). In this case as well, the position of the device andthe position of the user may differ by some small amount. Despite thesesmall differences in position, generally the position of themultifunction device and the position of the multifunction device usermay be considered to coincide.

In various embodiments, the map 314 a displayed by the multifunctiondevice may include one or more roads (e.g., roads 318 a-b), buildings(not illustrated), terrain features (e.g., hills, mountains) (notillustrated), parks (not illustrated), water bodies (not illustrated),and/or any other item that may be conveyed by a map. In some cases, themap may also include other map or navigation information including butlimited to readouts from one or more of a directional compass, analtimeter, and/or a thermometer.

In various embodiments, the mapping application may be configured togenerate directions from an origination (e.g., an address or a user'scurrent position) to a destination (e.g., an address, landmark,bookmarked/saved location, or point of interest). For instance, anindication of the origination and/or destination may be input into themulti function device by the user. The multifunction device may generateone or more candidate routes between those two points. The multifunctiondevice may select one of those routes for display on the device. Inother cases, multiple candidate routes may be presented to the user andthe user may select a preferred route. In the illustrated embodiment,one route is illustrated as route 320. The route may also includeturn-by-turn directions which may be presented to the user (in 2D or3D), such as a graphical indication to perform a turn 322 a from road318 a to road 318 b. In some embodiments, this graphical indication toperform a turn may be supplemented or substituted with an audibleindication to turn, such as a voice command from speaker 310 thatindicates the user is to “turn left in 100 yards,” for example. In someembodiments, the route that is selected may be presented to the user asa route overview. For instance, before proceeding with navigation, themultifunction device may generate a route overview display thatgraphically indicates key information for the route, such as key turns,route distance and/or an estimated time for traversing the route. Insome cases, the multifunction device may be configured to generate adisplay of driving maneuvers (e.g., turns, lane changes, etc.) thatoccur in quick succession, either in the route overview or during actualnavigation. This information may help the user safely prepare for suchmaneuvers. In some cases, the route information may be presented in alist format, such as a list of turns or other maneuvers.

In various embodiments, the mapping application of the multifunctiondevice may be configured to track the position of the user over time andcorrespondingly adjust the graphical position indicator 316 to indicatethe new position. For instance, the mapping application may determinethat the user is traveling along route 320 from position information(e.g., information from GPS module 135) and update the map 314 aaccordingly. For instance, in some cases the map 314 may remainstationary while position indicator 316 is moved along the route. Inother cases, position indicator 316 may remain stationary or “fixed”while map 314 is moved (e.g., panned, turned, etc.) around the positionindicator.

In various embodiments, the multifunction device may be configured todisplay alternate or contingency routes. In some cases, these routes maybe selectable by the user (e.g., via the touch screen interface). Inother cases, the multifunction device may select a best route based onone or more parameters, such as shortest distance or time. In somecases, these parameters or preferences may be set by the user.

As described in more detail below, the multifunction device may invarious embodiments receive routing information that specifies a routefrom a map service. In some case, the multifunction device may carry outnavigation guidance in accordance with this route. However, in somecases, the multifunction device may perform a reroute operation in orderto generate a new route to the destination. For instance, the user mayhave deviated from the original route or explicitly requested a newroute. In some cases, the multifunction device may perform reroutingbased on cached map data stored on the multifunction device.

In various embodiments, the multifunction device may be configured toperform route correction based on real-time data, such as updates in mapinformation, road conditions, traffic conditions, and/or weatherconditions. For instance, the multifunction device may be configured toalter a route such that the route avoids a construction zone or adangerous storm cell.

In various embodiments, the multifunction device may be configured toperform lane guidance independently or as part of navigation guidance.For instance, the multifunction device may, in response to detectingthat multiple turns follow in quick succession, provide the user with adirection or suggestion as to which lane to occupy. For instance, avoice or visual indication may specify that the user “turn right, thenmove to the left lane” in anticipation of a subsequent left turn. Inanother example, the multifunction device may detect one or more laneclosures (e.g., due to construction or other reasons) and instruct theuser to avoid such lanes.

In various embodiments, the multifunction device may be configured togenerate voice prompts for directions. For instance, during navigationguidance, the multifunction device may be configured to generate audiorepresentations of the next turn or driving maneuver on the route. Forinstance, the multifunction device may be configured to audibly indicatethe user should “turn left in 100 yards” or some other audibleindication of a maneuver.

In various embodiments, the multifunction device may be responsive tovarious voice commands for performing actions including a command toobtain a route. For instance, the multifunction device may interpret theuser's voice through a microphone or other transducer of themultifunction device. The user may specify an origination and adestination for the requested route. In various embodiments, themultifunction device may be configured to utilize the user's currentlocation as the origination for the route.

In various embodiments, the multifunction device may be configured toperform a search along a specific route, such as current navigationroute. For instance, the user of the multifunction device may requestthe location of points of interest, such as fuel stations orrestaurants. However, if a user is traveling along a particular route,they may not be particularly interested in points of interest that arenot proximate to that route. As such, the multifunction device may beconfigured to scope any searches to points of interested within aspecified distance away from the route. In various embodiments, thisdistance may be a configurable parameter.

In various embodiments, the multifunction device may be configured todisplay various graphical layers including but not limited to agraphical map information, aerial images (e.g., satellite-acquiredimages), and/or traffic information. For instance, in the trafficinformation example, the multifunction device may overlay color codedtraffic information on roadways to indicate the speed at which trafficis flowing. For example, green color coding may be used to indicatetraffic is flowing normally, and yellow or red may be used to indicatetraffic slowdowns.

In various embodiments, the multifunction device may be configured todisplay any quantity of metrics or statistics about a navigation routeincluding but not limited to an estimated time of arrival (ETA), traveldistance remaining, average speed (overall or moving average), topspeed, and/or other route statistics.

In various embodiments, the multifunction device may be configured todisplay routes at different angles in order to accommodate thepreferences of different users. Such viewing angles may include a birdseye view for two-dimensional maps to any of a variety of camera anglesavailable for a three-dimensional map.

In various embodiments, the multifunction device may be configured toprovide navigation information other than map and routing information.For instance the multifunction device may expose output from any of thehardware device described above with respect to FIG. 1. In onenon-limiting example, an orientation sensor 168 may include a compassthat outputs direction data. The multifunction device described hereinmay be configured to display this directional data as a virtual compass,for example.

Map Service Operating Environment

Various embodiments may operate within a map service operatingenvironment. FIG. 4 illustrates a map service operating environment,according to some embodiments. A map service 430 may provide mapservices for one or more client devices 402 a-402 c in communicationwith the map service 430 through various communication methods andprotocols. A map service 430 generally may provide map information andother map-related data, such as two-dimensional map image data (e.g.,aerial view of roads utilizing satellite imagery), three-dimensional mapimage data (e.g., traversable map with three-dimensional features, suchas buildings), route and direction calculation (e.g., ferry routecalculations or directions between two points for a pedestrian),real-time navigation data (e.g., turn-by-turn visual navigation data intwo or three dimensions), location data (e.g., where is the clientdevice currently located), and other geographic data (e.g., wirelessnetwork coverage, weather, traffic information, or nearbypoints-of-interest). In various embodiments, the map service data mayinclude localized labels for different countries or regions; localizedlabels may be utilized to present map labels (e.g., street names, citynames, points of interest) in different languages on client devices.Client devices 402 a-402 c may utilize these map services by obtainingmap service data. Client devices 402 a-402 c may implement varioustechniques to process map service data. Client devices 402 a-402 c maythen provide map services to various entities, including, but notlimited to, users, internal software or hardware modules, and/or othersystems or devices external to the client devices 402 a-402 c.

In some embodiments, a map service may be implemented by one or morenodes in a distributed computing system. Each node may be assigned oneor more services or components of a map service. Some nodes may beassigned the same map service or component of a map service. A loadbalancing node may distribute access or requests to other nodes within amap service. In some embodiments a map service may be implemented as asingle system, such as a single server. Different modules or hardwaredevices within a server may implement one or more of the variousservices provided by a map service.

A map service may provide map services by generating map service data invarious formats. In some embodiments, one format of map service data maybe map image data. Map image data may provide image data to a clientdevice so that the client device may process the image data (e.g.,rendering and/or displaying the image data as a two-dimensional orthree-dimensional map). Map image data, whether in two or threedimensions, may specify one or more map tiles. A map tile may be aportion of a larger map image. Assembling together the map tiles of amap may produce the original map. Tiles may be generated from map imagedata, routing or navigation data, or any other map service data. In someembodiments map tiles may be raster-based map tiles, with tile sizesranging from any size both larger and smaller than a commonly-used 256pixel by 256 pixel tile. Raster-based map tiles may be encoded in anynumber of standard digital image representations including, but notlimited to, Bitmap (.bmp), Graphics Interchange Format (.gif), JointPhotographic Experts Group (.jpg, .jpeg, etc.), Portable NetworksGraphic (.png), or Tagged Image File Format (.tiff). In someembodiments, map tiles may be vector-based map tiles, encoded usingvector graphics, including, but not limited to, Scalable Vector Graphics(.svg) or a Drawing File (.drw). Embodiments may also include tiles witha combination of vector and raster data. Metadata or other informationpertaining to the map tile may also be included within or along with amap tile, providing further map service data to a client device. Invarious embodiments, a map tile may be encoded for transport utilizingvarious standards and/or protocols, some of which are described inexamples below.

In various embodiments, map tiles may be constructed from image data ofdifferent resolutions depending on zoom level. For instance, for lowzoom level (e.g., world or globe view), the resolution of map or imagedata need not be as high relative to the resolution at a high zoom level(e.g., city or street level). For example, when in a globe view, theremay be no need to render street level artifacts as such objects would beso small as to be negligible in many cases.

A map service may perform various techniques to analyze a map tilebefore encoding the tile for transport. This analysis may optimize mapservice performance for both client devices and a map service. In someembodiments map tiles may be analyzed for complexity, according tovector-based graphic techniques, and constructed utilizing complex andnon-complex layers. Map tiles may also be analyzed for common image dataor patterns that may be rendered as image textures and constructed byrelying on image masks. In some embodiments, raster-based image data ina map tile may contain certain mask values, which are associated withone or more textures. Embodiments may also analyze map tiles forspecified features that may be associated with certain map styles thatcontain style identifiers.

Other map services may generate map service data relying upon variousdata formats separate from a map tile. For example, map services thatprovide location data may utilize data formats conforming to locationservice protocols, such as, but not limited to, Radio Resource Locationservices Protocol (RRLP), TIA 801 for Code Division Multiple Access(CDMA), Radio Resource Control (RRC) position protocol, or LTEPositioning Protocol (LPP). Embodiments may also receive or request datafrom client devices identifying device capabilities or attributes (e.g.,hardware specifications or operating system version) or communicationcapabilities (e.g., device communication bandwidth as determined bywireless signal strength or wire or wireless network type).

A map service may obtain map service data from internal or externalsources. For example, satellite imagery used in map image data may beobtained from external services, or internal systems, storage devices,or nodes. Other examples may include, but are not limited to, GPSassistance servers, wireless network coverage databases, business orpersonal directories, weather data, government information (e.g.,construction updates or road name changes), or traffic reports. Someembodiments of a map service may update map service data (e.g., wirelessnetwork coverage) for analyzing future requests from client devices.

Various embodiments of a map service may respond to client devicerequests for map services. These requests may be a request for aspecific map or portion of a map. Embodiments may format requests for amap as requests for certain map tiles. In some embodiments, requests mayalso supply the map service with starting locations (or currentlocations) and destination locations for a route calculation. A clientdevice may also request map service rendering information, such as maptextures or stylesheets. In at least some embodiments, requests may alsobe one of a series of requests implementing turn-by-turn navigation.Requests for other geographic data may include, but are not limited to,current location, wireless network coverage, weather, trafficinformation, or nearby points-of-interest.

A map service may, in some embodiments, may analyze client devicerequests to optimize a device or map service operation. For example, amap service may recognize that the location of a client device is in anarea of poor communications (e.g., weak wireless signal) and send moremap service data to supply a client device in the event of loss incommunication or send instructions to utilize different client hardware(e.g., orientation sensors) or software (e.g., utilize wireless locationservices or Wi-Fi positioning instead of GPS-based services). In anotherexample, a map service may analyze a client device request forvector-based map image data and determine that raster-based map databetter optimizes the map image data according to the image's complexity.Embodiments of other map services may perform similar analysis on clientdevice requests and as such the above examples are not intended to belimiting.

Various embodiments of client devices (e.g., client devices 402 a-402 c)may be implemented on different device types. Examples of aportable-multifunction device include the devices illustrated in FIGS. 1through 4, such as multifunction device 100 and multifunction device300. Client devices 402 a-402 c may utilize map service 430 throughvarious communication methods and protocols described below. In someembodiments, client devices 402 a-402 c may obtain map service data frommap service 430. Client devices 402 a-402 c may request or receive mapservice data. Client devices 402 a-402 c may then process map servicedata (e.g., render and/or display the data) and may send the data toanother software or hardware module on the device or to an externaldevice or system.

A client device may, according to some embodiments, implement techniquesto render and/or display maps. These maps may be requested or receivedin various formats, such as map tiles described above. A client devicemay render a map in two-dimensional or three-dimensional views. Someembodiments of a client device may display a rendered map and allow auser, system, or device providing input to manipulate a virtual camerain the map, changing the map display according to the virtual camera'sposition, orientation, and field-of-view. Various forms and inputdevices may be implemented to manipulate a virtual camera. In someembodiments, touch input, through certain single or combination gestures(e.g., touch-and-hold or a swipe) may manipulate the virtual camera.Other embodiments may allow manipulation of the device's physicallocation to manipulate a virtual camera. For example, a client devicemay be tilted up from its current position to manipulate the virtualcamera to rotate up. In another example, a client device may be tiltedforward from its current position to move the virtual camera forward.Other input devices to the client device may be implemented including,but not limited to, auditory input (e.g., spoken words), a physicalkeyboard, mouse, and/or a joystick.

Embodiments may provide various visual feedback to virtual cameramanipulations, such as displaying an animation of possible virtualcamera manipulations when transitioning from two-dimensional map viewsto three-dimensional map views. Embodiments may also allow input toselect a map feature or object (e.g., a building) and highlight theobject, producing a blur effect that maintains the virtual camera'sperception of three-dimensional space.

In some embodiments, a client device may implement a navigation system(e.g., turn-by-turn navigation). A navigation system provides directionsor route information, which may be displayed to a user. Embodiments of aclient device may request directions or a route calculation from a mapservice. A client device may receive map image data and route data froma map service. In some embodiments, a client device may implement aturn-by-turn navigation system, which provides real-time route anddirection information based upon location information and routeinformation received from a map service and/or other location system,such as Global Positioning Satellite (GPS). A client device may displaymap image data that reflects the current location of the client deviceand update the map image data in real-time. A navigation system mayprovide auditory or visual directions to follow a certain route.

A virtual camera may be implemented to manipulate navigation map dataaccording to some embodiments. Some embodiments of client devices mayallow the device to adjust the virtual camera display orientation tobias toward the route destination. Embodiments may also allow virtualcamera to navigation turns simulating the inertial motion of the virtualcamera.

Client devices may implement various techniques to utilize map servicedata from map service. Embodiments may implement some techniques tooptimize rendering of two-dimensional and three-dimensional map imagedata. In some embodiments, a client device may locally store renderinginformation. For example, a client may store a stylesheet which providesrendering directions for image data containing style identifiers. Inanother example, common image textures may be stored to decrease theamount of map image data transferred from a map service. Client devicesmay also implement various modeling techniques to render two-dimensionaland three-dimensional map image data, examples of which include, but arenot limited to: generating three-dimensional buildings out oftwo-dimensional building footprint data; modeling two-dimensional andthree-dimensional map objects to determine the client devicecommunication environment; generating models to determine whether maplabels are seen from a certain virtual camera position; and generatingmodels to smooth transitions between map image data. Some embodiments ofclient devices may also order or prioritize map service data in certaintechniques. For example, a client device may detect the motion orvelocity of a virtual camera, which if exceeding certain thresholdvalues, lower-detail image data will be loaded and rendered of certainareas. Other examples include: rendering vector-based curves as a seriesof points, preloading map image data for areas of poor communicationwith a map service, adapting textures based on display zoom level, orrendering map image data according to complexity.

In some embodiments, client devices may communicate utilizing variousdata formats separate from a map tile. For example, some client devicesmay implement Assisted Global Positioning Satellites (A-GPS) andcommunicate with location services that utilize data formats conformingto location service protocols, such as, but not limited to, RadioResource Location services Protocol (RRLP), TIA 801 for Code DivisionMultiple Access (CDMA), Radio Resource Control (RRC) position protocol,or LTE Positioning Protocol (LPP). Client devices may also receive GPSsignals directly. Embodiments may also send data, with or withoutsolicitation from a map service, identifying the client device'scapabilities or attributes (e.g., hardware specifications or operatingsystem version) or communication capabilities (e.g., devicecommunication bandwidth as determined by wireless signal strength orwire or wireless network type).

FIG. 4 illustrates one possible embodiment of an operating environment400 for a map service 430 and client devices 402 a-402 c. In someembodiments, devices 402 a, 402 b, and 402 c can communicate over one ormore wire or wireless networks 410. For example, wireless network 410,such as a cellular network, can communicate with a wide area network(WAN) 420, such as the Internet, by use of gateway 414. A gateway 414may provide a packet oriented mobile data service, such as GeneralPacket Radio Service (GPRS), or other mobile data service allowingwireless networks to transmit data to other networks, such as wide areanetwork 420. Likewise, access device 412 (e.g., IEEE 802.11g wirelessaccess device) can provide communication access to WAN 420. Devices 402a and 402 b can be any portable electronic or computing device capableof communicating with a map service, such as a portable multifunctiondevice described below with respect to FIGS. 1 to 4. Device 402 c can beany non-portable electronic or computing device capable of communicatingwith a map service, such as a system described below in FIG. 4.

In some embodiments, both voice and data communications can beestablished over wireless network 410 and access device 412. Forexample, device 402 a can place and receive phone calls (e.g., usingvoice over Internet Protocol (VoIP) protocols), send and receive e-mailmessages (e.g., using Simple Mail Transfer Protocol (SMTP) or PostOffice Protocol 3 (POP3)), and retrieve electronic documents and/orstreams, such as web pages, photographs, and videos, over wirelessnetwork 410, gateway 414, and WAN 420 (e.g., using Transmission ControlProtocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)).Likewise, in some implementations, devices 402 b and 402 c can place andreceive phone calls, send and receive e-mail messages, and retrieveelectronic documents over access device 412 and WAN 420. In variousembodiments, any of the illustrated client device may communicate withmap service 430 and/or other service(s) 450 using a persistentconnection established in accordance with one or more securityprotocols, such as the Secure Sockets Layer (SSL) protocol or theTransport Layer Security (TLS) protocol.

Devices 402 a and 402 b can also establish communications by othermeans. For example, wireless device 402 a can communicate with otherwireless devices (e.g., other devices 402 a or 402 b, cell phones) overthe wireless network 410. Likewise devices 402 a and 402 b can establishpeer-to-peer communications 440 (e.g., a personal area network) by useof one or more communication subsystems, such as Bluetooth®communication from Bluetooth Special Interest Group, Inc. of Kirkland,Wash. 402 c can also establish peer to peer communications with devices402 a or 402 b. (not pictured). Other communication protocols andtopologies can also be implemented. Devices 402 a and 402 b may alsoreceive Global Positioning Satellite (GPS) signals from GPS 440.

Devices 402 a, 402 b, and 402 c can communicate with map service 430over the one or more wire and/or wireless networks, 410 or 412. Forexample, map service 430 can provide a map service data to renderingdevices 402 a, 402 b, and 402 c. Map service 430 may also communicatewith other services 450 to obtain data to implement map services. Mapservice 430 and other services 450 may also receive GPS signals from GPS440.

In various embodiments, map service 430 and/or other service(s) 450 maybe configured to process search requests from any of the client devices.Search requests may include but are not limited to queries for business,address, residential locations, points of interest, or some combinationthereof. Map service 430 and/or other service(s) 450 may be configuredto return results related to a variety of parameters including but notlimited to a location entered into an address bar or other text entryfield (including abbreviations and/or other shorthand notation), acurrent map view (e.g., user may be viewing one location on themultifunction device while residing in another location), currentlocation of the user (e.g., in cases where the current map view did notinclude search results), and the current route (if any). In variousembodiments, these parameters may affect the composition of the searchresults (and/or the ordering of the search results) based on differentpriority weightings. In various embodiments, the search results that arereturned may be a subset of results selected based on specific criteriainclude but not limited to a quantity of times the search result (e.g.,a particular point of interest) has been requested, a measure of qualityassociated with the search result (e.g., highest user or editorialreview rating), and/or the volume of reviews for the search results(e.g., the number of times the search result has been review or rated).

In various embodiments, map service 430 and/or other service(s) 450 maybe configured to provide auto-complete search results that may bedisplayed on the client device, such as within the mapping application.For instance, auto-complete search results may populate a portion of thescreen as the user enters one or more search keywords on themultifunction device. In some cases, this feature may save the user timeas the desired search result may be displayed before the user enters thefull search query. In various embodiments, the auto complete searchresults may be search results found by the client on the client device(e.g., bookmarks or contacts), search results found elsewhere (e.g.,from the internet) by map service 430 and/or other service(s) 450,and/or some combination thereof. As is the case with commands, any ofthe search queries may be entered by the user via voice or throughtyping. The multifunction device may be configured to display searchresults graphically within any of the map display described herein. Forinstance, a pin or other graphical indicator may specify locations ofsearch results as points of interest. In various embodiments, responsiveto a user selection of one of these points of interest (e.g., a touchselection, such as a tap), the multifunction device may be configured todisplay additional information about the selected point of interestincluding but not limited to ratings, reviews or review snippets, hoursof operation, store status (e.g., open for business, permanently closed,etc.), and/or images of a storefront for the point of interest. Invarious embodiments, any of this information may be displayed on agraphical information card that is displayed in response to the user'sselection of the point of interest.

In various embodiments, map service 430 and/or other service(s) 450 mayprovide one or more feedback mechanisms to receive feedback from clientdevices 402 a-c. For instance, client devices may provide feedback onsearch results to map service 430 and/or other service(s) 450 (e.g.,feedback specifying ratings, reviews, temporary or permanent businessclosures, errors etc.); this feedback may be used to update informationabout points of interest in order to provide more accurate or moreup-to-date search results in the future. In some embodiments, mapservice 430 and/or other service(s) 450 may provide testing informationto the client device (e.g., an AB test) to determine which searchresults are best. For instance, at random intervals, the client devicemay receive and present two search results to a user and allow the userto indicate the best result. The client device may report the testresults to map service 430 and/or other service(s) 450 to improve futuresearch results based on the chosen testing technique, such as an AB testtechnique in which a baseline control sample is compared to a variety ofsingle-variable test samples in order to improve results.

In various embodiments, other services 450 may also include a collectionservice 452 configured to collect and aggregate signal strengthinformation from client devices (e.g., client devices 402 a-c). Otherservices 450 may also include a coverage service 454 configured togenerate a signal strength map based on the information collected bycollection service 452. Other service 450 may also include a routeanalyzer service 456 configured to analyze a signal strength map and acandidate route to generate a map tile priority. In regard to otherservice 452-456, additional description of functionality is described inmore detail below.

Aggregate Coverage Information

As described above, a collection service 452 may be configured tocollect and aggregate signal strength information from client devices(e.g., client devices 402 a-c). FIG. 5A illustrates a flow diagram ofcollection service 452 receiving a signal strength message from a clientdevice 500, which may be similar to any of the multifunction devicesdescribed above (e.g., client devices 402 a-c). In various embodiments,as a given client device 500 is transferred about (e.g., while its useris walking or driving), the client device may periodically oraperiodically report signal strength information to a collection service452. One example of this signal strength information is signal strengthmessage 502. In the illustrated embodiment, the signal strength messagemay include a device and/or user identifier, information specifying alocation or position of the device (e.g., coordinates in the illustratedexample), and a measure of signal strength measured by the client deviceat that location or position. In various embodiments, the client devicemay utilize a positioning component (e.g., GPS module 135) to determinethe coordinates or other location information to be included within themessage. In various embodiments, the signal strength message may alsoinclude information about the network that was measured for signalstrength. In the illustrated embodiment, this network information ispresented as a network identifier (e.g., information identifying acellular or WiFi network) although in other embodiments additionalinformation about the network may be specified. In some cases, someinformation illustrated as part of the signal strength message may beomitted; in some cases, addition information may be included. In variousembodiments, collection service 452 may store the client-reported signalstrength messages, such as within signal strength information data store504. This signal strength information may be evaluated by the coverageservice to generate a signal strength map as described in more detailbelow.

FIG. 5B illustrates the creation of a signal strength heat map by thecoverage service. In various embodiments, coverage service 454 mayreceive aggregated signal strength information 510 (e.g., from signalstrength information data store 504) for a particular region. Forinstance, the aggregated signal strength information may include anaggregation of the signal strength messages for the particular region.The coverage service 454 may be configured to generate a signal strengthmap based on this aggregated signal strength information. For clarity ofillustration, the illustrated signal strength map is represented as aheat map in which darker shading indicates higher signal strengthrelative to areas of lighter shading. While the illustrated embodimentsrepresent the signal strength map in the format of a heat map, otherembodiments may generate graphical representations of signal strengthmap in other graphical configurations.

To generate data points for the signal strength heat map, the coverageservice may perform one or more statistical analyses on the signalstrength information for various locations including individualpositions (e.g., a point position) or an area/region. For instance, fora given location, coverage service 454 may generate the mean or mediansignal strength value from the n-most signal strength values for thatlocation. In other cases, different analyses and associated signalvalues (e.g., maximum signal values or quartile signal values) may beconveyed on the signal strength heat map.

Note that in the illustrated embodiments the signal strength heat mapneed not be generated as a graphical representation. For instance, thesignal strength heat map may be generated as a data structure definingthe heat map (e.g., a data structure from which a graphicalrepresentation may be generated). In another example, the signalstrength heat map may be generated as a database (or other model) forautomated evaluation of signal strength values at different locations.

FIG. 5C illustrates a flowchart of an example method for generating aheat map of signal strength values. As illustrated at block 520, themethod may include receiving location and signal strength data points.For instance, in some embodiments, such a data point might includeinformation from the signal strength messages described above includingbut not limited to information specifying a location or position of aclient device, and a measure of signal strength measured by the clientdevice at that location or position. As illustrated at block 522, themethod may also include performing one or more statistical analyses onthe signal strength information for various locations (e.g., a pointposition or an area/region) to generate map data points. For instance,for a given location, the method may include generating the mean ormedian signal strength value from the n-most signal strength values forthat location. In other cases, different statistical or numericalanalyses may be used on the client-reported signal strength informationin order to generate the map data points or values that populate theheat map. As illustrated at block 524, the method may include generatingthe signal strength heat map based on the values resulting form the oneor more statistical analyses. For instance, the method may includegenerating the heat map by plotting the mean or median signal values asdifferent colors or shades. In one non-limiting example, the method mayinclude generating a signal strength heat map in which darker shadingindicates higher signal strength relative to areas of lighter shading(e.g., signal strength heat map 512).

Route Analysis and Map Tile Priority

FIG. 6A-6C illustrate techniques for using the signal strength maps toidentify a given route's weak or dead spots, which may include locationslacking requisite signal strength for a desired level of data transfer,such as may be used for acquisition of map tiles from a mapping service(e.g., map service 430). These weak spots may influence the order of maptile priority 604, which as described in subsequent Figures may definethe order in which map tiles are acquired from a map service. In FIG.6A, route analyzer service 454 may be configured to receive a route 600.In various embodiments, route 600 may include a route for directions ornavigation guidance requested by a client device (described in moredetail with respect to 7A). Route analyzer service 454 may also receivea signal strength heat map 602 representing an area inclusive of route600. Signal strength heat map 602 may be generated utilizing thetechniques described above with respect to signal strength heat map 512.Route analyzer service 454 may be configured to perform one or morecomparative analyses on route 600 and signal strength heat map 602 togenerate a map tile priority 604. These comparative analyses aredescribed in more detail below with respect to FIG. 6B.

Generally the map tile priority 604 may specify a priority for map tilesin which map tiles representing zones of no signal strength or weaksignal strength (e.g., as defined by a configurable threshold signalstrength value) are assigned a higher priority than map tilesrepresenting zones having the requisite signal strength for a desiredlevel of data transfer (e.g., data transfer for the client devicesacquisition of map tiles from the map service). As described in moredetail with respect to subsequent Figures, client devices may use thismap tile priority for requesting map tiles as well as evicting map tilesfrom the client's local cache. For instance, map tiles of a higherpriority (e.g., areas of worse signal strength) may be requested beforethe traversal of a route as these tiles may be difficult to retrievewhen the client device is located in areas of poor signal strength. Maptiles of a lower priority (e.g., areas having the requisite signalstrength for map tile acquisition on-the-fly) may be downloaded enroute.

FIG. 6B illustrates a graphical representation of the techniquesutilized to identify the priority of different map tiles; thesetechniques may be utilized by route analyzer service 454 to generate amap tile priority, such as map tile priority 604. In the illustratedembodiment a superimposed heat map 610 may be generated by overlayingroute 600 on top of signal strength heat map 602. As illustrated, route600 intersects areas of different signal strength (e.g., differentshaded zones, darker shades representing higher signal strength). Forclarity of illustration, the illustrated signal strength map isrepresented as a heat map in which darker shading indicates highersignal strength relative to areas of lighter shading. Map tiles 612represent the tiles to be downloaded onto the client device in order todisplay the requisite map information (e.g., raster-based orvector-based map information) for the route. Generally these map tilesmay be defined as tiles representing areas within some configurabledistance from the route. As illustrated, map tiles 612 may also beoverlaid on the signal strength heat map in their respective locations.The route analyzer service 454 may be configured to assign a priority toeach map tile based on the strength of the signal strength zone that themap tile overlaps. The route analyzer may include rules for handling maptiles overlapping an intersection of two different signal strengthzones, such as assigning the lowest overlapping signal strength to themap tile. In the illustrated embodiments, the map tiles associated withareas having the lowest signal strength may be assigned the highestpriority in map tile priority 604. For instance, map tiles residing inareas of little or no signal strength, which are illustrated asdead/weak zones 614 a-c in the illustrated embodiment, may be assignedthe highest priority. In another example, tiles within a signal-richzone may be assigned the lowest priority as the map tiles may bedownloaded en route (e.g., on-the-fly) over a wireless data connection.

FIG. 6C illustrates a flowchart of an example method for generating amap tile prioritization. As illustrated, block 620 may includegenerating a route 620, such as by utilizing the techniques describedabove with respect to map service 430. Generally generating a route mayinclude identifying an efficient travel path between an origination anda destination. As illustrated at block 622, the method may includecomparing the route to a signal strength map to identify map tiles inzones of different signal strength. For instance, this portion of themethod may include overlaying a representation of the route on thesignal strength map, such as described above with respect tosuperimposed heat map 610. This portion of the method may also includeidentifying the map tiles relevant to the route, such as map tileswithin a requisite distance from the route. The method may includeassigning a priority to each map tile based on the strength of thesignal strength zone that the map tile overlaps. The method may alsoinclude enforcing rules for handling map tiles overlapping anintersection of two different signal strength zones of the signalstrength map, such as rule that specifies the lowest overlapping signalstrength is to be assigned to the map tile. As illustrated by block 624,the method may also include creating the map tile priority by rankingmap tiles. For instance, map tiles residing in areas of little or nosignal strength may be assigned the highest ranking within the priority.Tiles within a signal-rich zone may be assigned the lowest priority asthe map tiles may be downloaded en route (e.g., on-the-fly) over awireless data connection. One example of a map tile priority that may begenerated with the illustrated method includes map tile priority 604,which is described above.

While FIGS. 6A-6C provide examples for generating a map tile priority,FIGS. 7A-7B illustrate techniques for utilizing the map tile priorityfor a client device's efficient acquisition of map tiles for a givenroute. For instance, FIG. 7A illustrates a dataflow diagram for a clientdevice's acquisition of map tiles based on the map tile prioritydescribed herein. In the illustrated embodiments, client device 700(e.g., similar to the client devices and multifunction devices describedabove) may issue a route request 702 to map service 430 in accordancewith any of the techniques described above. In response, map service 430may determine the route and associated map tile priority according tothe techniques described above, and also provide the route and tilepriority 704 to the client device. Instead of requesting map tilesequentially, client device 700 may instead request map tiles via maptile request 706 on the basis of priority as specified by the receivedmap tile priority. For instance, the map tile priority may specify apriority order for map tiles in which map tiles representing zones of nosignal strength or weak signal strength (e.g., as defined by aconfigurable threshold signal strength value) are assigned a higherpriority than map tiles representing zones having the requisite signalstrength for a desired level of data transfer (e.g., data transfer forthe client devices acquisition of map tiles from the map service). Theclient device may download map tiles 708 provided by the map service 430in response to map tile request 706.

In some embodiments, the mapping component of client device 700 mayutilize the map tile priority to identify the highest priority map tiles(e.g., map tiles for areas of the worst signal strength) and requestthese tiles before (or during the initial phase of) route guidance. Inthis way, these high priority map tiles may be cached before the clientdevice ever reaches the areas of poor signal strength. In variousembodiments, lower priority tiles (e.g., map tiles associated with areashaving sufficient signal strength for data transfer) may be downloadeden route (e.g., “on-the fly”).

FIG. 7B illustrates an example method for map tile acquisition. Invarious embodiments, the illustrated method may be performed by any ofthe client devices described herein. As illustrated by block 710, themethod may include requesting a route for direction or route guidance(e.g., navigation). In various embodiments, the route request mayspecify an origination and a destination between which a user desires totravel. In various embodiments, requesting a route may include sending arequest to a map service, such as described above with respect to routerequest 702. Subsequent to the request, the method may include receivingan indication of the route and an associated map tile priority, asillustrated at block 712. In various embodiments, the method may includereceiving a map tile priority structured in a manner similar to that ofmap tile priority 604 described above. For instance, the map tilepriority may specify a priority for map tiles in which map tilesrepresenting zones of no signal strength or weak signal strength areassigned a higher priority than map tiles representing zones having therequisite signal strength for a desired level of data transfer.

As illustrated at block 714, the method may include downloading maptiles for areas of no signal strength or poor signal strength beforeother tiles in accordance with the map tile priority. For instance, themethod may include using the map tile priority to identify the highestpriority map tiles (e.g., map tiles for areas of the worst signalstrength) and request these tiles before (or during the initial phaseof) route guidance. In this way, these high priority map tiles may becached before reaching the areas of poor signal strength. In variousembodiments, lower priority tiles (e.g., map tiles associated with areashaving sufficient signal strength for data transfer) may be downloadeden route.

FIG. 7C illustrates another example method for map tile acquisitionusing check-points. In various embodiments the illustrated method may beutilized as a substitute to the method of FIG. 7B. In other cases,aspects of each method may be combined to perform a hybrid approach tomap tile acquisition (e.g., the method of FIG. 7B may be augmented withthe check-pointing technique of FIG. 7C). In various embodiments, theillustrated method may be performed by any of the client devicesdescribed herein. As illustrated at block 720, the method may includerequesting a route for route guidance. In various embodiments, the routerequest may specify an origination and a destination between which auser desires to travel. In various embodiments, requesting a route mayinclude sending a request to a map service, such as described above withrespect to route request 702. Subsequent to the request, the method mayinclude receiving an indication of the route, as illustrated at block724. For instance, the route may specify driving directions from theorigination to the destination. As illustrated at block 724, the methodmay also include downloading map tiles for the first segment of theroute. For instance, the route may be logically partitioned intodifferent route segments (e.g., 10 kilometer segments) and the first ofthese segments may be downloaded and cached (e.g., onto a clientdevice).

At block 726 the method may include determining whether the download ofadditional map information is critical at the current position withinthe route traversal. For instance, the method may include monitoring thedistance to the next portion of the route for which tiles have not beenobtained. If this distance falls below a specified threshold, the methodmay determine that it is critical to download (or at least attempt todownload) tiles for that portion of the route regardless of the currentsignal reception of the client device. As illustrated by the positiveoutput of block 726, when additional map information is determined to becritical, the method may proceed to block 732 in which map tiles for thenext route segment are downloaded. As illustrated by the negative outputof block 726, if it is determined that additional map information is notcritical, the method may evaluate whether a checkpoint has been reached(block 728). For instance, the client device may place multiplecheckpoints (e.g., specified by time or distance) along the route. Forinstance, in a non-limiting example, a checkpoint may be placed every 3kilometers of travel. In other cases checkpoints may be specifiedtemporally (e.g., every two minutes a checkpoint is active). Asillustrated by the negative output of block 728, if a checkpoint has notbeen reached, the method returns to block 726.

If a checkpoint has been reached (positive output of block 728), themethod may include evaluating whether the current signal strengthmeasured by the client device is above a threshold (e.g., a signalthreshold known to provide efficient data transfer speeds), the methodmay opportunistically download map tiles for the next route segment atblock 732. Using checkpoints to optimistically download map tilesaccording to the techniques described herein may conserve power (e.g.,battery power) on the client device implementing the method. Forinstance, by optimistically downloading map tiles during periods ofstrong signal reception, the map tiles may be downloaded faster due tohigher transfer speeds associated with the strong signal reception. Thismeans the communication radio of the client device may be active forshorter periods of time, thereby causing a power to be conserved on thedevice. As illustrated at block 734, if there are more map segments leftin the route, the method may return to block 726. If there no more mapsegments to be retrieved, the method may end, as illustrated by thenegative output of block 734.

Cache Management

In various embodiments, the map tile priority described above may alsobe utilized to efficiently manage the client device's cache of maptiles. One example method for managing the cache of a client device isillustrated at block 800 of FIG. 8. In various embodiments, theillustrated method may be performed by any of the client devicesdescribed herein. As illustrated at block 800, the method may includedetermine whether a cache eviction threshold has been reached. Forinstance, the cache eviction threshold may specify a threshold thatindicates the cache is nearly full and more storage room needs to beopened up for additional entries to be written to the cache. In onenon-limiting example, the cache eviction threshold may specify that thecache is nearly full when 90% of the cache storage space is occupied. Asillustrated by the negative output of block 800, the method may includecontinuing to monitor the cache until the threshold is reached. Asillustrated by the positive output of block 800, the method may includeevicting (e.g., removing or deleting) one or map tiles based onassociated signal strength such that map tiles associated with highersignal strength are evicted before map tiles associated with lowersignal strength (block 802). In this way, the cache eviction techniquemay efficiently utilize the cache by preserving map tiles that areharder to acquire (e.g., tiles associated with areas of poor signalcoverage) and evicting (if necessary) map tiles that are easier toacquire (e.g., map tiles associated with areas of adequate signalcoverage). In various embodiments, for a given route, the method mayinclude utilizing the map tile priority provided by the map service(e.g., map tile priority 604) in order to determine which map tiles areassociated with higher signal strength and which map tiles areassociated with lower signal strength. For instance, as described abovethe map tile priority may specify a priority for map tiles in which maptiles representing zones of no signal strength or weak signal strength(e.g., as defined by a configurable threshold signal strength value) areassigned a higher priority than map tiles representing zones having therequisite signal strength for a desired level of data transfer (e.g.,data transfer for the client devices acquisition of map tiles from themap service).

Example Computer System

Various embodiments of the system and method for generating signalcoverage information from client metrics, as described herein, may beexecuted on one or more computer systems, which may interact withvarious other devices. Note that any component, action, or functionalitydescribed above with respect to FIGS. 1-8 may be implemented on one ormore computers configured as computer system 900 of FIG. 9, according tovarious embodiments. In the illustrated embodiment, computer system 900includes one or more processors 910 coupled to a system memory 920 viaan input/output (I/O) interface 930. Computer system 900 furtherincludes a network interface 940 coupled to I/O interface 930, and oneor more input/output devices 950, such as cursor control device 960,keyboard 970, and display(s) 980. In some cases, it is contemplated thatembodiments may be implemented using a single instance of computersystem 900, while in other embodiments multiple such systems, ormultiple nodes making up computer system 900, may be configured to hostdifferent portions or instances of embodiments. For example, in oneembodiment some elements may be implemented via one or more nodes ofcomputer system 900 that are distinct from those nodes implementingother elements.

In various embodiments, computer system 900 may be a uniprocessor systemincluding one processor 910, or a multiprocessor system includingseveral processors 910 (e.g., two, four, eight, or another suitablenumber). Processors 910 may be any suitable processor capable ofexecuting instructions. For example, in various embodiments processors910 may be general-purpose or embedded processors implementing any of avariety of instruction set architectures (ISAs), such as the x86,PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. Inmultiprocessor systems, each of processors 910 may commonly, but notnecessarily, implement the same ISA.

System memory 920 may be configured to store program instructions 922and/or data 932 accessible by processor 910. In various embodiments,system memory 920 may be implemented using any suitable memorytechnology, such as static random access memory (SRAM), synchronousdynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type ofmemory. In the illustrated embodiment, program instructions 922 may beconfigured to implement a mapping application 924 incorporating any ofthe functionality described above. Additionally, data 932 of memory 920may include mapping information 934 including any of the information ordata structures described above, including but not limited to mappinginformation for rendering map instances (e.g., map tiles), positioninformation indicating past or current positions of the user, and/orroute information for navigating from an origination to a destination.In some cases, mapping information 934 may represent a map tile cache.In some embodiments, program instructions and/or data may be received,sent or stored upon different types of computer-accessible media or onsimilar media separate from system memory 920 or computer system 900.While computer system 900 is described as implementing the functionalityof functional blocks of previous Figures, any of the functionalitydescribed herein may be implemented via such a computer system.

In one embodiment, I/O interface 930 may be configured to coordinate I/Otraffic between processor 910, system memory 920, and any peripheraldevices in the device, including network interface 940 or otherperipheral interfaces, such as input/output devices 950. In someembodiments, I/O interface 930 may perform any necessary protocol,timing or other data transformations to convert data signals from onecomponent (e.g., system memory 920) into a format suitable for use byanother component (e.g., processor 910). In some embodiments, I/Ointerface 930 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of I/Ointerface 930 may be split into two or more separate components, such asa north bridge and a south bridge, for example. Also, in someembodiments some or all of the functionality of I/O interface 930, suchas an interface to system memory 920, may be incorporated directly intoprocessor 910.

Network interface 940 may be configured to allow data to be exchangedbetween computer system 900 and other devices attached to a network 985(e.g., carrier or agent devices) or between nodes of computer system900. Network 985 may in various embodiments include one or more networksincluding but not limited to Local Area Networks (LANs) (e.g., anEthernet or corporate network), Wide Area Networks (WANs) (e.g., theInternet), wireless data networks, some other electronic data network,or some combination thereof. In various embodiments, network interface940 may support communication via wired or wireless general datanetworks, such as any suitable type of Ethernet network, for example;via telecommunications/telephony networks such as analog voice networksor digital fiber communications networks; via storage area networks suchas Fibre Channel SANs, or via any other suitable type of network and/orprotocol.

Input/output devices 950 may, in some embodiments, include one or moredisplay terminals, keyboards, keypads, touchpads, scanning devices,voice or optical recognition devices, or any other devices suitable forentering or accessing data by one or more computer systems 900. Multipleinput/output devices 950 may be present in computer system 900 or may bedistributed on various nodes of computer system 900. In someembodiments, similar input/output devices may be separate from computersystem 900 and may interact with one or more nodes of computer system900 through a wired or wireless connection, such as over networkinterface 940.

As shown in FIG. 9, memory 920 may include program instructions 922,which may be processor-executable to implement any element or actiondescribed above. In one embodiment, the program instructions mayimplement the methods described above. In other embodiments, differentelements and data may be included. Note that data 932 may include anydata or information described above.

Those skilled in the art will appreciate that computer system 900 ismerely illustrative and is not intended to limit the scope ofembodiments. In particular, the computer system and devices may includeany combination of hardware or software that can perform the indicatedfunctions, including computers, network devices, Internet appliances,PDAs, wireless phones, pagers, etc. Computer system 900 may also beconnected to other devices that are not illustrated, or instead mayoperate as a stand-alone system. In addition, the functionality providedby the illustrated components may in some embodiments be combined infewer components or distributed in additional components. Similarly, insome embodiments, the functionality of some of the illustratedcomponents may not be provided and/or other additional functionality maybe available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 900 may be transmitted to computer system900 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network and/or a wireless link. Various embodiments mayfurther include receiving, sending or storing instructions and/or dataimplemented in accordance with the foregoing description upon acomputer-accessible medium. Generally speaking, a computer-accessiblemedium may include a computer-readable storage medium or memory mediumsuch as magnetic or optical media, e.g., disk or DVD/CD-ROM, volatile ornon-volatile media such as RAM (e.g. SDRAM, DDR, RDRAM, SRAM, etc.),ROM, etc. In some embodiments, a computer-accessible medium may includetransmission media or signals such as electrical, electromagnetic, ordigital signals, conveyed via a communication medium such as networkand/or a wireless link.

The methods described herein may be implemented in software, hardware,or a combination thereof, in different embodiments. In addition, theorder of the blocks of the methods may be changed, and various elementsmay be added, reordered, combined, omitted, modified, etc. Variousmodifications and changes may be made as would be obvious to a personskilled in the art having the benefit of this disclosure. The variousembodiments described herein are meant to be illustrative and notlimiting. Many variations, modifications, additions, and improvementsare possible. Accordingly, plural instances may be provided forcomponents described herein as a single instance. Boundaries betweenvarious components, operations and data stores are somewhat arbitrary,and particular operations are illustrated in the context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within the scope of claims that follow. Finally,structures and functionality presented as discrete components in theexemplary configurations may be implemented as a combined structure orcomponent. These and other variations, modifications, additions, andimprovements may fall within the scope of embodiments as defined in theclaims that follow.

What is claimed is:
 1. A computer-implemented method, comprising:receiving, by a map service implemented on one or more servers, a routerequest from a client communication device that is remote from the oneor more servers implementing the map service; determining, by the mapservice, a route corresponding to the route request; identifying, by themap service, one or more relevant map tiles of a set of map tiles for aregion that includes the route, wherein the one or more relevant maptiles are within a requisite distance from the route; assigning, by themap service, respective values to individual ones of the one or morerelevant map tiles based at least in part on at least one expectedsignal strength value for at least one location within a signal strengthmap for the region that corresponds to the respective individual one ofthe relevant map tiles; and subsequent to determining the route andassigning the respective values, providing, by the map service, theroute and an indication of the respective values of the individual onesof the one or more relevant map tiles to the client communicationdevice.
 2. The computer-implemented method of claim 1, furthercomprising: receiving, by the map service, signal strength informationreported by multiple client communication devices of a plurality ofclient communication devices, wherein the signal strength informationreported by a given client communication device indicates: one or morelocations detected by the given client communication device, and foreach location a respective measure of signal strength for acommunication signal detected at that location by the clientcommunication device; and generating, by the map service, the signalstrength map for the region based on the reported signal strengthinformation, wherein the generating the signal strength map comprises:for each location of multiple locations within the region, generating anexpected signal strength value for that location based on an evaluationof the signal strength information received for that location; andgenerating the signal strength map for the region based on the expectedsignal strength values for the locations within the region.
 3. Thecomputer-implemented method of claim 2, wherein the evaluation of thesignal strength information for the locations of the region comprises:for each location of the region, performing a statistical analysis onthe reported signal strength information for that location in order togenerate the expected signal strength value for that location.
 4. Thecomputer-implemented method of claim 3, wherein performing a statisticalanalysis on the client reported signal strength values of the regioncomprises generating a mean signal strength value or median signalstrength value for one or more locations within the region.
 5. Thecomputer-implemented method of claim 2, wherein the communicationsignals detected by the multiple client communication devices includeone or more of: a cellular signal or a wireless signal for a networkgateway.
 6. The computer-implemented method of claim 2, furthercomprising generating the signal strength map as one or more of:information specifying a graphical representation of a signal strengthmap, or a database of locations and respective signal strength values.7. The computer-implemented method of claim 2, wherein the receivedsignal strength information includes measured signal strengths forcommunication devices operating on networks of different wirelesscarriers, and wherein said generating the signal strength map comprisesgenerating a different signal strength map for each wireless carrier. 8.The computer-implemented method of claim 3, wherein said performing thestatistical analysis comprises generating one or more of: mean signalstrength values for different locations, or median signal strengthvalues for different locations.
 9. A system, comprising: one or morememories; and one or more processors coupled to the one or morememories, wherein the one or more memories comprise program instructionsexecutable by the one or more processors to implement one or moreservices configured to: receive a route request from a client devicethat is remote from the system; determine a route corresponding to theroute request; identify one or more relevant map tiles of a set of maptiles for a region that includes the route, wherein the one or morerelevant map tiles are within a requisite distance from the route;assign respective values to individual ones of the one or more relevantmap tiles based at least in part on at least one expected signalstrength value for at least one location within a signal strength mapfor the region that corresponds to the respective individual one of therelevant map tiles; and provide, subsequent to said determine the routeand said assign the respective values, the route and an indication ofthe respective values of the individual ones of the one or more relevantmap tiles to the client device.
 10. The system of claim 9, wherein theprogram instruction are configured to: receive signal strengthinformation reported by multiple client devices of a plurality of clientdevices, wherein the signal strength information reported by a givenclient device indicates: one or more locations detected by the givenclient device, and for each location a respective measure of signalstrength for a communication signal detected at that location by theclient device; and generate the signal strength map for the region basedon the reported signal strength information, wherein to generate thesignal strength map the program instructions are further configured to:for each location of multiple locations within the region, generate anexpected signal strength value for that location based on an evaluationof the signal strength information received for that location; andgenerate the signal strength map for the region based on the expectedsignal strength values for the locations within the region; wherein thereceived messages include measured signal strengths for devicesoperating on networks of different wireless carriers; and wherein theprogram instructions are further configured to generate a differentsignal strength map for each wireless carrier.
 11. The system of claim10, wherein to perform the one or more statistical analyses on themessages, the program instructions are configured to generate one ormore of: mean signal strength values for different locations, or mediansignal strength values for different locations.
 12. The system of claim10, wherein each of the expected signal strength values representexpected signal strength at one or more of: a point location or aregion.
 13. The system of claim 10, wherein each of the expected signalstrength values represent expected signal strength at one or more of: apoint location or a region.
 14. The system of claim 10, wherein for eachof multiple cell sites within a region represented by the signalstrength map, the program instructions are configured to: generate oneor more expected signal strength values for that cell site.
 15. Thesystem of claim 14, wherein the method comprises, responsive to arequest specifying a particular cell site, the program instructions areconfigured to: provide an expected signal strength value for a locationproximate to the particular cell site.
 16. The system of claim 10,wherein said multiple client devices include one or more of: asmartphone, a tablet device, a touch-responsive electronic device, or amobile computer.
 17. The system of claim 10, wherein one or more of theclient-reported messages specify position coordinates determined basedon one or more of: cell site triangulation, or a global positioningsystem (GPS).
 18. A non-transitory, computer-readable storage medium,storing program instructions that are executable on a computer to:receive a route request from a client device that is remote from thecomputer executing the program instructions; determine a routecorresponding to the route request; identify one or more relevant maptiles of a set of map tiles for a region that includes the route,wherein the one or more relevant map tiles are within a requisitedistance from the route; assign respective values to individual ones ofthe one or more relevant map tiles based at least in part on at leastone expected signal strength value for at least one location within amodel of wireless network coverage for the region that corresponds tothe respective individual one of the relevant map tiles; and provide,subsequent to said determine the route and said assign the respectivevalues, the route and an indication of the respective values of theindividual ones of the one or more relevant map tiles to the clientdevice.
 19. The non-transitory, computer-readable storage medium ofclaim 18, wherein the programs are executable on the computer to:receive from each of a plurality of mobile communication devices thatare remote from the computer executing the program instructions, one ormore messages each comprising position information specifying a positionand coverage information indicating a level of wireless network coverageat that position; based on the received messages, generate the model ofwireless network coverage for the region, wherein the model specifiesexpected levels of wireless network coverage for different positionswithin said region; and evaluate the model to determine an expectedlevel of wireless network coverage for a particular position within theregion.
 20. The non-transitory, computer-readable storage medium ofclaim 18, wherein the model comprises a database of positions andassociated expected levels of wireless network coverage.